@bryan-dort
Forum Replies Created
-
AuthorReplies
-
Cloverleaf 6.1.1 has been released and is available on the Infor Download Center. Some of the new features of Cloverleaf 6.1.1 that you will want to check out:
* xlate debugger
* tcl script editor
* revision control
* SMAT database live-search
These are really significant enhancements for a patch-level update. There are other enhancements and fixes.
—
Bryan Dort, PMP
Infor ICS Consultant, Principal
Cloverleaf Services
The database-inbound protocol does not move the db cursor to read the next set of records. It runs the sql statement that you have defined, then runs the sql statement again at the interval that you have defined.
You are most likely seeing the same records being retrieved from the database at every interval.
In order to eliminate the records that you have already read from being read again, you should create a read success action to update the database for those records with some type of flag or date/time stamp. Then on your original sql, use that same flag to condition the reading of the records (WHERE).
Bryan
Words cannot express the gratitude that I feel for Jim and his patience and guidance on this site. He is truly one-of-a-kind and this post was long overdue. Thanks for posting this.
Bryan
For Customer Assistance with Infor Cloverleaf Integration Suite, or any other Infor products, please contact our excellent support professionals using your Infor Xtreme Support account at http://www.inforxtreme.comhttp://www.inforxtreme.com” class=”bbcode_url”> Bryan Dort, PMP
Senior Technical Consultant
Infor
June 29, 2012 at 5:19 pm in reply to: copy entire hl7 message to a single xml field within xlate? #76782I see it now. Thanks.
Bryan
June 29, 2012 at 4:37 pm in reply to: copy entire hl7 message to a single xml field within xlate? #76780The topic of this thread was asking how to take an entire HL7 and put it into one XML field. But the code you posted breaks out the individual fields and builds the XML. Why wouldn’t you do that in the xlate?
June 29, 2012 at 3:27 pm in reply to: copy entire hl7 message to a single xml field within xlate? #76776You should be able to do this all through the xlate gui. You could define the input as a VRL with a single field. With the output the XML. Then copy that VRL to the element in the XML.
You are correct…5.8.5.0 is the current, highest release that is generally available. My mistake.
Bryan
Kevin,
You can untar the file to a directory under root, then install from there. You will need to make sure that you download the latest patch for CIS on AIX…which I believe at the time of this writing 5.8.5.4. The patch will need to be installed as hci user, so be sure to make it available to that user.
To obtain a license, send a request to crm3@lawson.com for a license key. When you receive the license key form, fill in the information, including your host ID. Return the form to crm3@lawson.com. Your license key will be processed and sent to you with instructions on where to install it.
Call support if you have further issues with the install. The install instructions are being updated for the next release.
Bryan
There is one in the $HCIROOT/contrib directory called fileset_dir_parse.tcl that you can modify to fit your needs.
Bryan
We moved from McKesson to Lawson (Heathvision) direct support at the end of 2009, and couldn’t be happier with the decision.
There were a couple of reasons for the change:
1.) we had replaced all of our McKesson products with other products and it didn’t make sense to keep support active for just one product…when they weren’t even the developers of that product.
2.) updates to Cloverleaf took too long for McKesson to certify for their products. Why wait for certification of products if we no longer have any of their products?
McKesson support was adequate and they responded well to any calls I made. They were a great partner with us for many years. However, to us, it made more business sense to get answers “straight from the horse’s mouth.”
Bryan
Ironically, I needed to setup this exact scenario today.
Couple things. In your xlate, the SUPPRESS should be at the top of the xlate and the CONTINUE within the ITERATE for the FT1:
SUPPRESS
…
INTERATE
PATHCOPY 1(%g1).0(0).FT1 -> 1(0).0(0).FT1 *** You don’t need the %g1 in the destination as you only want one FT1…it won’t repeat.
COPY =1 -> {1(0).0(0).FT1.00355[0]} *** This will put a 1 in the sequence number…since you only want one FT1…it won’t repeat and will always be 1.
CONTINUE
Warning…there was talk in earlier posts about PATHCOPY in iterates not clearing fields. You may want to switch to individual COPY statements.
Bryan
You should not use the recover_56 procs with any other version before 5.6. As for the 5.5 issues, you may want to start a new thread specifically for 5.5 or search for one. Since I skipped 5.5, I’m not going to be much help. -
AuthorReplies
